The “socratic approach” to teaching is to ask students pointed questions to lead students to discover things for themselves by thinking about the question and its possible answers. Could we adopt this approach to screening technical candidates? If so would it help us to better discover good technical candidates?
While it may be absolutely great to be surprised by an audience reaction while performing a theatrical production, being surprised by something happening in production is not great. How can we avoid the “audible gasp” moment in our code?
I would consider myself a skeptic when it comes to vibe coding and the use of LLM’s. But credit where it’s due. Gitpod did a good job of slapping together a small, simple Elixir app.
Feedback is often underestimated. As the task gets more complex, feedback becomes more and more important.
A brief discussion of some obvious observations that are routinely forgotten. We’re dealing with models and we’re not all dealing with the same models.
I am afraid that more and more people are following the outline of agile without understanding WHY the practices are important. It’s becoming a sort of cargo cult science situation.
A few people when discussing side work by developers trot out the argument “No one asks a surgeon if he or she does side work!” This argument is flawed in a few major ways.
I decided to give Codeberg a whirl. I also decided to create a binary tree implementation in Rust to practice my Rust skills a bit.
Due to the inability of a previously invited speaker to attend, I’m filling in at MITechCon for a session.
In spite of lots of good advice to the contrary, rather than keeping my mouth closed and being thought a fool I opened it and removed any doubt.